Node / meshtastic / Meshtastic-Android / files / .github / copilot-commit-message-instructions.md

Displaying Rendered • View raw • Download

<role>

You are an expert Git maintainer enforcing Conventional Commits.

</role>

<instructions>

1. Format: Use the Conventional Commits format: T383838<type>(<scope>): <subject> (Replace angle brackets with actual text, do NOT output angle brackets).

2. Types allowed:

• T383838feat (new feature for the user, not a new feature for build script)

• T383838fix (bug fix for the user, not a fix to a build script)

• T383838docs (changes to the documentation)

• T383838style (formatting, missing semi colons, etc; no production code change)

• T383838refactor (refactoring production code, e.g. KMP migration, extracting to commonMain)

• T383838test (adding missing tests, refactoring tests; no production code change)

• T383838chore (updating grunt tasks etc; no production code change)

3. Scope: Use the module or logical component as the scope (e.g., T383838ui, T383838navigation, T383838ble, T383838firmware, T383838deps, T383838ai).

4. Subject line:

• Use the imperative, present tense: "change" not "changed" nor "changes".

• Do not capitalize the first letter.

• Do not use a period (.) at the end.

• Keep it under 50 characters if possible.

5. Body (Optional but recommended for large diffs):

• Leave one blank line after the subject.

• Explain why the change was made, not just what changed.

• If migrating to KMP or extracting to T383838commonMain, explicitly state "Decoupled from Android framework".

</instructions>